Implementation Workflow of Isolated License Managers

The implementation of isolated License Managers is based on the concept of a unique software vendor identifier that differentiates one software vendor’s License Manager from the another. This ensures that the License Manager instances of each software vendor operate in parallel, along with their configuration settings and related files. Therefore time and consideration should be spent on choosing, setting, and using the same software vendor specific identifier:

>Choosing the Vendor Identifier
The software vendor identifier needs to be a unique string consisting maximum of 25 alphanumeric characters.

>Setting the Vendor Identifier
The software vendor identifier is set during the License Manager customization using the API function VLSenableVendorIsolation. Refer to Appendix B - Customization Features of the Sentinel RMS SDK API Reference Guide for details about the function.
Also remember to customize the network port of the isolated License Manager (see: Using a communication port other than 5093). Refer to the Appendix B - Customization Features“ of the Sentinel RMS SDK API Reference Guide for details.

>Using the Vendor Identifier
The customized License Manager service name (on Windows) will have the software vendor identifier appended, separated by an underscore (_). See an example of a Windows-based isolated License Manager below, which has the V1 string appended.

Figure 1: Isolated License Manager (Windows)

All the isolated License Manager generated files will have the software vendor identifier appended in the same manner. The isolated License Manager files will be generated at the same locations as the generic License Manager, but will have the designated suffix.

Also, the input files used by the isolated License Manager and associated environment variables must carry the same suffix, in the same format. It is the software vendor's responsibility to properly educate a system administrator with this information.